VIDIZMO Upload Node
The VIDIZMO Upload Node uploads files from workflow execution to your VIDIZMO platform's blob storage, making them accessible for content publishing and processing. It supports single or batch file uploads with chunked transfer for large files and automatic retry logic for transient network failures. The node returns download and playback URLs for uploaded content, enabling downstream nodes to reference files in subsequent operations.
How It Works
The VIDIZMO Upload node transfers files from the workflow execution environment to your VIDIZMO platform's blob storage using authenticated API calls. When the node executes, it validates that all specified file paths exist and are accessible within the tenant's secure temporary folder. The node then establishes a connection to your VIDIZMO instance using your user authentication token and tenant domain from the workflow runtime context, ensuring uploads are properly authorized and routed to the correct tenant storage.
For each file, the node performs a three-phase chunked upload process. First, it initializes the upload session with VIDIZMO storage. Second, it reads the file in chunks and uploads them in parallel to maximize throughput while managing memory efficiently. Third, it commits all uploaded chunks to finalize the file. This chunked approach enables reliable uploads of large files with automatic retry logic for transient network failures. The upload process respects configured concurrency limits to balance speed with resource usage.
Upon successful upload, the node returns detailed information for each file including download URLs, playback URLs, and storage metadata. This information is stored in the specified output variable, making it immediately available for downstream nodes to reference the uploaded files in subsequent operations like mashup publishing or content processing. If configured to continue on failure, the node processes all files and returns results for successful uploads while logging errors for failed ones.
Configuration Parameters
Output Field
Output Field (Text, Required): Workflow variable where upload results are stored.
The output is an array of upload results, one for each successfully uploaded file. Each result contains download URLs, playback URLs, blob name, file size, and storage metadata. The download URL provides direct access to the file, while playback URLs enable streaming for media files.
Common naming patterns: upload_results, uploaded_files, blob_urls
File Paths
File Paths (Array, Required): File path or list of file paths to upload.
Provide a single file path string or an array of file paths for batch uploads. All files must exist in the workflow execution environment and be accessible within the tenant's temporary folder. Variable interpolation with ${file_path} or ${file_paths} is supported for dynamic file selection based on previous workflow operations.
Content File Name
Content File Name (Text, Optional): Prefix path for organizing uploaded files in blob storage.
When specified, files are uploaded as {contentFileName}/{localFileName}. For example, with prefix transcripts/2024, a file meeting.vtt uploads as transcripts/2024/meeting.vtt. Leave empty to upload files with their original names at the storage root. Variable interpolation with ${prefix} is supported.
Common Parameters
This node supports common parameters shared across workflow nodes, including Stream Output Response, Streaming Messages, and Logging Mode. For detailed information, see Common Parameters.
Best Practices
- Store file paths in workflow variables rather than hardcoding them for reusable and maintainable workflows
- Use the Content File Name prefix to organize uploaded files by logical groupings like date, workflow type, or content category to simplify file management and prevent naming conflicts
- Enable continue on failure for workflows processing multiple files to capture partial results and identify only the failed uploads for retry
- Monitor workflow execution time and adjust timeout settings when uploading large files or many files simultaneously
- Store returned URLs in workflow variables for use in subsequent nodes like mashup publishing to maintain references throughout workflow execution
Limitations
- File path security: Files must be located within the tenant's temporary folder in the workflow execution environment. Attempts to upload files from other locations fail with a security error.
- Timeout configuration: The node uses a hidden timeout parameter (default 5 minutes, maximum 10 minutes) that cannot be configured through the UI. Very large file uploads may timeout before completion.
- Chunk configuration: Chunk size and max concurrency parameters are hidden in the UI and use default values (4MB chunks, 4 parallel uploads). These cannot be adjusted without backend configuration changes.
- Content type: All uploaded files are assigned a default content type of "Misc". Specific content type assignment requires subsequent mashup publishing operations.